ci: [7.x] packaging pipeline job #18001
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kuisathaverat
changed the title
cachedout
approved these changes
Apr 27, 2020
mdelapenya
reviewed
Apr 27, 2020
|
|
||
| def withBeatsEnv(Closure body) { | ||
| def os = goos() | ||
| def goRoot = "${env.WORKSPACE}/.gvm/versions/go${GO_VERSION}.${os}.amd64" |
There was a problem hiding this comment.
I assume we are not building 32bit flavours, right?
There was a problem hiding this comment.
I guess this Go installation is only needed for mage, actual packaging is run inside the golang-crossbuild image.
mdelapenya
approved these changes
Apr 27, 2020
jsoriano
approved these changes
Apr 27, 2020
botelastic
bot
added
the
needs_team
mdelapenya
added
the
Team:Automation
botelastic
bot
removed
the
needs_team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
It adds a new pipeline to make the packaging
Why is it important?
It replaces the multi-job we use for each branch and pull request, so everything will be in a single job, and the job logic in a Jenkinsfile.
related #16603 #17563